Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[Resolved] AGGL-6074: Android devices may fail to update IMEI and/or serial number on UEM console (75666)

Last Updated: 9/11/2020Categories: TroubleshootingTotal Views: 10117Language:
JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Console administrators may note that devices using Android 10 and later are not sending IMEI and serial number information to the Workspace ONE UEM Console upon enrolling.

Version Identified

Android 10 and later

Impact / Risks

Major functionalities are impacted by this issue:

Allowlist: Allowlist records are created based on IMEI, Serial Number and/or  UDID to allow device enrollment. In this case, enrollment will be blocked for allowed devices.

Denylist: Denylist records are created based on IMEI, Serial Number, and/or UDID to deny devices from getting enrolled. In this case, devices will be enrolled successfully.

Registered Devices Only Mode: If Device Enrollment Mode is set to Registered Devices Only and registration record is created with the IMEI, Serial Number, and/or UDID, device enrollment will be blocked.

Resolution

Enrollment restrictions for IMEI & Serial Number are now supported for Android 10+ enrolling into Android Enterprise for UEM v2005. These enrollment restrictions will be evaluated during enrollment for Fully Managed devices.

While for Work Profile enrollment, the data needed to evaluate the restriction isn’t collected until after the user has finished enrolling the device, meaning if the restriction check fails, the user may be unenrolled with a message letting them know that the enrollment restriction check has failed and they are not allowed to enroll that device.

Workaround

Issue has been resolved in UEM 2005.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
インスタント クローン プールのプロビジョニングが失敗し、内部テンプレートがエラー状態になる (76140)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE

Related Versions:

Take Our Survey

Support Assistant